Only available for Logged-in member. Please login or register to access this information.Or use the Temporary User that we have provided to you via email.
expiry time
Replaced by
WSLRW-MB485 | FW3
Manual for WSLRW-MB485 | FW3
Replaced by
Item codes | FW Released Date | Changes Information |
|---|---|---|
WSLRW-MB485-01 | 25/01/2025 | Update payload Cyclic, Force (39 bytes ) with SF7-SF9 for AS923, AU915, US915 and SF7-SF12 for EU868, IN865, RU864, KR920); Note: ; +SF9 => Datagram interval >= 30; +SF12 => Datagram interval >= 120 |
1
QUICK INSTALLATION GUIDE
1.1 Introduction
WSLRW-MB485 is a LoRaWAN node with an RS485 master port to connect to any sensor, water meter, power meter, gas meter, or flow computer with an RS485 slave port. The device supports fieldbus protocols of Modbus RTU. The device is configurable via offline software and downlink messages. Ultra-low-power design and smart firmware allow the sensor to run on a 2 x AA battery 1.5V for 10 years with one update per day. The sensor will transmit data over kilometers to the LoRaWAN gateway, any brand on the market. It supports all LoRaWAN frequency bands.
How the sensor connect to system?
System components:
The end nodes are LoRaWAN Sensors or Actuators;
The Gateways are LoRaWAN Gateway or Base Station;
The Network Server can be SAAS or On-premise server;
The Application Server is the destination software users want to utilize the data from/ to LoRaWAN sensors/ actuators.
How to set up the LoRaWAN system? Please follow these steps:
Adding the Gateways to a Network server. Please refer to the manual of Gateway and Network Server software;
Adding the End nodes to the Network Server;
Configure the callback or data forwarding from the Network Server to the Application Software by MQTT or HTTPS. Please refer to the manual of the Network Server.
Once the payload is on the Application server, decode data from Payload. Please check Section 1.9 for the Payload document.
1.2 Application Notes
For Applications
Electric Meter Reading, Gas Meter Reading, Water Meter Reading, Production Monitoring, Facility Monitoring
Notes
Data Rate and Distance: Ensure it supports the required data rate and distance for your application.
Power Supply Voltage: Check compatibility with your system's power supply.
ESD Protection: Look for built-in protection against voltage spikes.
Operating Temperature Range: Ensure it suits your application's environment.
Unit Load: Lower unit loads allow more devices on the bus.
Package Type: Ensure it fits your design's space constraints.
Noise Immunity: Evaluate for performance in noisy environments.
1.3 When does device send Uplink messages?
The device will send uplink messages in the following cases:
Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device.
Case 2: Then, in every interval time (pre-configured), for example, 10 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...
To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.
Case 3: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s.
Case 4: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.
Case 5: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 6: If LNS_CHECK_MODE =1, it will send the confirmed uplink message called LNS_CHECK every 24 hours. This confirmed uplink message is a message where a LoRaWAN device is requesting a LoRaWAN network to confirm the reception of its message. If the device receives no confirmation message from LoraWAN network server, it will re-send the LNS_CHECK message every hour during 3 hours. After 4th hour, if the device still receives no confirmation message, it will reset itself to join the network server. The LNS_CHECK payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 7: If the application/network server sends downlink 3 to check current value of a configuration parameter or sends downlink type 5 to change value of a configuration parameter, the device will send the CONFIG-CHECK uplink. The payload of CONFIG-CHECK uplink contains the result of the configuration changes/configuration check.
1.4 Default Configuration
This MB485 converter has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete node(converter+ wireless) delivers the proper output value. Please check the Payload document for more information.
1.5 Battery/ Power Supply
The Device uses below batteries:
Battery type: Primary battery
Battery size and Voltage: AA 1.5 VDC
Number of batteries: 02
Recommended batteries: Energizer® L91 or equivalent from Duracell;
Please take note on the Polarity of the batteries as below picture.
Re-install the housing, pay attention to put the PCB edge into the middle guiding slot of the box inside as shown below)
Understanding the battery levels:
Level 3 (4 bars): battery energy is 60-99%
Level 2 (3 bars): battery energy is 30-60%
Level 1 (2 bars): battery energy is 10-30%
Level 0 (1 bar): battery energy is 0-10%
1.6 What's in the Package?
1.7 Guide for Quick Test
With the default configuration, the device can be connected quickly to the Network Server by the following steps.
Step 1: Prepare the values of communication settings
Frequency zone: Most of the sensor was configured the frequency zone to suit customer application before delivery
DevEUI: Get the DevEUI on the product nameplate
AppEUI Default value: 010203040506070809
AppKey Default value: 0102030405060708090A0B0C0D0E0F10
Activation Mode: OTAA with local join server
Network Mode: Public
LoraWAN Protocol: version1.0.3
Class: A for sensor; C for actuator
If current basic common settings do not match with your region, network server/application, follow below instruction to change them as below:
For changing other settings, please refer to Section 3.2 Sensor configuration to change the other settings
Step 2: Register the device on the LoRaWAN network server
Input the above settings on your device registration page of the network server.
Note: Different network server software will have different device registration processes. Please refer to the manual of the network server software used for more details.
Please visit the below Section 1.10 to get the instructions for adding the LoRaWAN sensors to some common network servers such as Actility, TTN...
Step 3: Install the batteries to the device OR do power wiring and supply external power to the device if applicable
Please refer to Section 1.5 as above for instructions on battery installation OR for instructions to do power wiring and supply external power to the the device if applicable
After installing the battery in 60 seconds, the first data packet will be sent to the LoRaWAN gateway. After receiving the first data packet, the time of another packet depends on the value of the parameter: cycle_send_data. Additionally, you can use a magnet key to touch the magnetic switch point on the housing within 1 second to initiate force packet of the device to send data instantly and the LEDs on the housing will be lit with SKY BLUE color.
Step 4: Decode the payload of receiving package
Please refer to Section 1.9 Payload Document and Configuration Tables for details of decoding the receiving packet to get the measured values.
If the device has local display, measured values are shown on the local display
1.8 Installation
Dimension Drawings and Installation Gallery (Photos and Videos)
Please follow the checklist below for a successful installation:
1. Have you studied the dimensions of the device as above drawings?
2. Have you tested and make sure the device have been connected successfully as Section "1.7 Guide for Quick Test" above?
3. Have the device been configured properly as per Section 3.2 below?
4. Have the device been calibrated or validated as per Section 3.3 below?
5. Then you can start to install the device at site. Please check the following Installation Notes for Sensor Part (if available) before installation.
Installation Notes for Sensor Part (if available)
Key installation notes for an RS485 converter:
1. Wiring:
- Twisted Pair Cables: Use twisted pair cables to minimize electromagnetic interference (EMI).
- Termination Resistors: Install termination resistors (typically 120 ohms) at both ends of the RS485 bus to prevent signal reflections.
2. Grounding:
- Proper Grounding: Ensure proper grounding of the RS485 network to avoid ground loops and reduce noise.
3. Network Topology:
- Daisy-Chain Configuration: Use a daisy-chain (bus) configuration for connecting devices. Avoid star or ring topologies.
4. Device Addressing:
- Unique Addresses: Assign unique addresses to each device on the RS485 network to prevent communication conflicts.
5. Power Supply:
- Stable Power Supply: Ensure a stable power supply to the RS485 transmitter to maintain reliable communication.
6. Environmental Considerations:
- Temperature and Humidity: Install the transmitter in an environment within its specified temperature and humidity range.
6. Other Considerations:
- Check Compatibility: Verify that the RS485 transmitter is compatible with the other devices and the overall system.
- Follow Manufacturer Guidelines: Always follow the manufacturer's installation guidelines and safety instructions.
Installation Guide for Main Device
Check the Location for the best RF Signal
Make sure the site is good enough for RF signal transmission.
Tip: To maximize the transmission distance, the ideal condition is Line-of-sight (LOS) between the LoRaWAN Node and the gateway. In real life, there may be no LOS condition. However, the LoRaWAN Node still communicates with the gateway, but the distance will be reduced significantly.
DO NOT install the wireless Node or its antenna inside a completed metallic box or housing because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.
Mounting the Device on the Wall or Pole
Mount the Node onto a wall by the mounting bracket with provided bracket and screws.
LoraWAN main device is connected to RS485 Modbus slave via M12 female connector.
Wiring of M12 female connector:
Note:
The LoRaWAN Modbus Node only output power supply when POWER_OUTPUT_MODE is configured to 2 or 3.
1.9 Payload Document and Configuration Tables
Please click below button for:
-
Payload decoding of Uplink messages;
-
Payload encoding of Downlink messages;
-
Configuration Tables of device.
Note:
If the content of below web payload, memory map, and sample decoder could not be copied, please install the extension of "Enable Copy Paste - E.C.P" for Microsoft Edge and for Google Chrome.
1.10 How to connect device to Back-end/ Network Server/ Coordinator
Please find below the examples of adding Daviteq's LoRaWAN sensor to the following Network servers:
ThingPark Community (of Actility);
Things Stack (of The Things Network).
You can use the similar methods to add LoRaWAN sensors to other Network Server.
1. THINGPARK COMMUNITY (ACTILITY) NETWORK SERVER
1.1. Example to add the Tektelic LoraWAN gateway Model T0005204 to ThingPark Enterprise SaaS Community
1. Log in to your ThingPark Enterprise account via the link: https://community.thingpark.io/tpe/
2. Browse on the left panel to Base Stations, click the drop-down menu, then click Create.
3. Select the base station’s Tektelic.
※ If you do not find the Tektelic, click View More Manufacturers.
4. On the following screen, select the Model: Micro 8-channels from the drop-down list.
5. Fill the form as below table:
Input exactly as above Input field column, except Name field is user-defined and is different from the existing base station name on the network server.
After filling the registration form, click CREATE to complete adding the base station to the network server.
1.2. Add Daviteq's LoRaWAN devices to ThingPark Enterprise SaaS Community
ThingPark Enterprise supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server that is programmed at the factory.
Manual provisioning of OTAA devices using a local Join Server. To learn more, see Activation modes.
1. At left panel of the screen of the Thingpark GUI, click Devices > Create from the dashboard.
2. Select the Generic supported by your device on your screen.
3. Select the Model of LoRanWAN 1.0.3 revA - class A with correct frequency plan
4. Fill the form as below table:
In addition to filling out the form, the option to select the connection between ThingPark and Daviteq application (Globiots).
After filling out the registration form, please click CREATE to add devices to the network server.
1.3. Send a downlink frame from Thingpark Network Server to the device
Follow the below steps to send the downlink frame from Thingpark Network Server to the device:
This functionality is active only when a connection is associated to the device (one of the color codes with a green bullet).
1. Navigate to the left panel, click the Devices' drop-down menu, then click List.
2. Browse the right side in the Devices, click the icon of the device and click Send Downlink.
3. Input the downlink code to the Payload field and input 1 to the Port field, and then click Validate.
The downlink data is added to the device downlink queue in network server. The downlink is sent after the network server receive an uplink from the device.
2. THINGS STACK (THE THINGS NETWORK) NETWORK SERVER
2.1. Add Sentrius LoraWAN gateway (Model RG19) to The things Stack network server
1. Log in to you’re The Things Stack account
2. Click the tab Gateways, click Add gateway button
3. Fill out the form as below table:
Input exactly as above Input column, except the Gateway Name field and the Gateway ID field is user-defined. It is different from the existing gateway name and gateway ID on the network server.
After filling the registration form, click Create gateway to complete adding the base station to the network server.
2.2. Add Daviteq's LoRaWAN device to The Things Stack network server
The Things Stack supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server programmed at the factory.
1. Browse on the top panel, click the tab Application, and click Add application button to create an application
2. Fill in the information fields as user-defined, then select Create application
3. After the application is created successfully, select Add end device to register end device (LoRaWAN sensor)
4. Fill out the form as below table:
After filling out the registration form, please click the Register end device button to add the device to the network server.
2.3. Send a downlink frame from The Things Stack Network Server to the device
1. Select the device to send downlink
2. Input 1 to the FPort and input the downlink data in the payload field, and then tick Confirmed downlink and click Schedule downlink.
2
MAINTENANCE
2.1 Troubleshooting
Please find below steps to identify the problems from Communication Part or Sensor Part:
* If the device cannot connect to the Gateway or System or Co-ordinator at the first time, it is the Communication Problem;
* If the device status like battery, RSSI level, data status or other communication is normal, but the measured values are not updated or wrong, it would be the problems of Sensor part;
* If the data coming to gateway, system or co-ordinator is not frequently as expected, the problem would be Communication.
Please refer below the troubleshooting guide for Communication and Sensor Part.
Troubleshooting for Communication
Troubleshooting for Sensor Part (if available)
Important troubleshooting tips for an RS485 converter:
Check Wiring and Connections:
Ensure all connections are secure and that A+ and B- communication cables are correctly connected throughout the network.
Verify Termination Resistors:
Confirm that termination resistors (typically 120 ohms) are installed at both ends of the RS485 bus to prevent signal reflections.
Inspect Grounding:
Proper grounding is essential to avoid ground loops and reduce noise. Check that the network is properly grounded.
Check Communication Parameters:
Verify that all devices on the network are configured with the same baud rate, parity, stop bits, and data bits.
Monitor for Noise and Interference:
Use twisted pair cables to minimize electromagnetic interference (EMI). Check for sources of electrical noise that could affect communication.
Test with Known Good Devices:
Replace the RS485 transmitter with a known good device to determine if the issue is with the transmitter or another part of the network.
Check for Biasing Resistors:
Ensure that biasing resistors are correctly installed if required by your network configuration.
Review Device Configuration:
Confirm that each device has a unique address and that there are no address conflicts on the network.
2.2 Maintenance
Maintenance for Main device
There is no requirement for maintenance of the Hardware of LoRaWAN Device except:
1. The battery needs to be replaced. Please check the battery status via uplink messages;
Note: When the battery indicator shows only one bar (or 10% remaining capacity), please arrange to replace the battery with a new one as soon as possible. If not, the battery will drain completely, and the resulting chemical leakage can cause severe problems with the electronic circuit board.
Maintenance for Sensor part (if available)
Maintenance guidelines for an RS485 converter:
1. Regularly inspect wiring and connections to ensure they are secure and free from damage.
2. Check termination resistors at both ends of the RS485 bus to prevent signal reflections.
3. Verify proper grounding to avoid ground loops and reduce noise.
4. Periodically review communication parameters (baud rate, parity, stop bits, data bits) to ensure consistency across all devices.
5. Monitor for sources of electrical noise and use twisted pair cables to minimize interference.
6. Test the transmitter with known good devices to identify potential issues.
7. Ensure biasing resistors are correctly installed if required by your network configuration.
8. Keep the transmitter in an environment within its specified temperature and humidity range.
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for device WSLRW-MB485 | FW3
Daviteq LoRaWAN RS485 Master (MB485) Node comprises 02 parts linked internally:
• The Daviteq LoraWAN wireless transmitter;
• The Daviteq LoRaWAN RS485 Master (MB485) Node
What are the primary output values?
• SLAVE ADDRESS: Address of slave device. This parameter equals SLAVE_ADDRESS in the uplink payload
• FUNCTION CODE: Modbus function code to the parameter. This parameter equals FUNCTION_CODE in the uplink payload
• REGISTER ADDRESS: Start address of the Modbus parameter. This parameter equals REGISTER_ADDRESS in the uplink payload
• MODBUS CMD EXCEPTION: Exception of the Modbus command (0: OK; 15: Timeout). This parameter equals MODBUS_CMD_EXCEPTION in the uplink payload
• ALARM VALUE: Value of the parameter to trigger the alarm. This parameter equals ALARM_VALUE in the uplink payload
• DATA VALUE: Value of the parameter in Modbus command. This parameter equals DATA_VALUE in the uplink payload
• MESSAGE INDEX: Ordinal number of Message. This parameter equals MESSAGE_INDEX in the uplink payload
• TENTATIVE: Tentative number is the number of continuous alarm cycles. If the number of continuous alarm cycles is greater than 255, the Tentative keep value of 255. This parameter equals TENTATIVE in the uplink payload
• ALARM COMMAND ID: ID of configured Modbus command in alarm uplink. This parameter equals ALARM_COMMAND_ID in the uplink payload
What are the secondary output values?
Below output values are useful for device maintenance and troubleshooting.
• HW VERSION: Hardware version. This parameter equals HW_VERSION in the uplink payload
• FW VERSION: Firmware version. This parameter equals FW_VERSION in the uplink payload
• CURRENT CONFIGURATION: Latest received and valid downlink frame;=CURRENT_CONFIGURATION on device memory map. Detail of CURRENT_CONFIGURATION is at G. MODBUS MEMORY MAP section. This parameter equals CURRENT_CONFIGURATION in the uplink payload
• POWER LEVEL: Power Supply Level (External power or battery ), unit of %. This parameter equals POWER_LEVEL in the uplink payload
• START ADDRESS: The start address of the configuration to check. This parameter equals START_ADDRESS in the uplink payload
• NUM OF REGISTER: Number of register of the configuration to check. This parameter equals NUM_OF_REGISTER in the uplink payload
• CONTENT OF REGISTER: Content of configuration, in hexadecimal format. This parameter equals CONTENT_OF_REGISTER in the uplink payload
Principle of operation
Cyclic data uplink
Most of the time, the device will be in sleep mode. When the timer reaches the CYCLIC_DATA_PERIOD (for example, 30 minutes), it will wake up the device to start implement pre-configured Modbus commands and return the result on the Node' memory map and send CYCLIC_DATA uplink to Network Server. Details of the uplink is in section 1.9 Payload and memory map tables
Other uplinks
The device send the main configurations in START_UP , PARAMTERS_UPDATE and HEARTBEAT uplinks. In additions, the device send LNS_CHECK uplink to check LoRaWAN network server, and send CONFIG_CHECK uplink to check current value of device's other configurations
Modbus command configurations to read/write Modbus RTU slave device via downlink type 1, port 1 (default)
Downlink type 1 structure as below
Where:
SLAVE_ADDRESS: Address of slave device
FUNCTION_CODE: Modbus function code to the parameter
REGISTER_ADDRESS: Start address of the parameter
BYTE_ORDER: BYTE_ORDER = 0.
NUMBER_OF_REGISTERS: Number of register for the parameter, max 27
reserved8: Reserved for future usage
CMD_CONFIG_#: Ordinal number of command configuration 1-31.
reserved4: Reserved for future usage
DOWNLINK_TYPE: Downlink type equal to 1
Details of downlink type type 1 is in section 1.9 Payload and memory map tables
Modbus command configurations to read/write Modbus RTU slave device via offline tool
Refer section 3.2 Configuration for instruction to use offline configuration tool
Write value of downlink type 1 to corresponding CMD_CONFIG_Y ( where Y =0 - 31) on device memory map
Notes:
To clear corresponding a Modbus command Y, write the hex value of 00 00 00 00 01 00 XX 01 to corresponding CMD_CONFIG_Y (where XX is hex value of Y, Y = 0-31)
How to implement read Modbus command of slave device
The device will implement read Modbus command for FORCE uplink, CYCLIC_DATA uplink based on pre-configured read Modbus commands in CMD_CONFIG_0 to CMD_CONFIG_31
How to implement write Modbus command of slave device
The device will implement written Modbus command when the device receive the downlink type 5 to write the value to corresponding WRITTEN_VALUE_FOR_CMD_Y based on pre-configured written Modbus commands in CMD_CONFIG_Y (where Y = 0 - 31). Details of downlink type 5 is in section 1.9 Payload and memory map tables
Principle of Operation of Sensor part (if available)
The converter with RS485 Modbus RTU protocol is widely used in industrial automation and control systems. Here's a brief overview of its principal operation:
RS485 Communication Protocol
- Differential Signaling: RS485 uses differential signaling to transmit data, which helps in reducing noise and allows communication over long distances (up to 1200 meters).
- Multi-Drop Network: It supports a multi-drop network, meaning multiple devices (up to 32) can be connected on the same bus.
- Half-Duplex and Full-Duplex Modes: RS485 can operate in both half-duplex (one-way communication at a time) and full-duplex (simultaneous two-way communication) modes.
Modbus RTU Protocol
- Master-Slave Architecture: Modbus RTU operates on a master-slave architecture where the master device initiates communication and the slave devices respond.
- Message Structure: Each Modbus RTU message consists of:
- Slave Address: Identifies the slave device.
- Function Code: Specifies the action to be performed (e.g., read or write data).
- Data: Contains the actual data or parameters for the function.
- CRC Checksum: Ensures data integrity by detecting errors in transmission
- Registers and Coils: Data in Modbus RTU is organized into registers and coils, which can be read from or written to by the master device.
Default Configuration Parameters of Sensor part (if available)
This MB485 converter has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete node(converter+ wireless) delivers the proper output value. Please check the Payload document for more information.
3.2 Configuration
How to configure the device?
Sensor configuration can be configured in 02 methods:
Method 1: Configuring via Downlink messages, port 1 (default).
Method 2: Configuring via Offline cable.
Step to access configuration port: Open housing by turning counter-clockwise 2 hex screws, then remove the anti-interference shield, the configuration port as below figure:
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
Which Parameters are configured?
Please check Part G in Section 1.9 Payload Documents above.
Method 1: Configuration via Downlink messages
Please check the Part D & E in Section 1.9 Payload Documents above.
Method 2: Configuration by Offline Cable
Please download the Configuration Template File of this sensor to be used in Step 4 below.
Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
1. Prepare equipment and tools
The following items must be prepared for configuration.
A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
A Modbus configuration cable
Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)
2. Download and launch Daviteq Modbus configuration software
Click the link below to download Daviteq Modbus configuration software:
https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs
After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use.
Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:
Note: The software only runs on Microsoft Windows OS (Windows 7 and above).
3. Connect the cable and configure the sensor
Step 1:
Connect the PC to the sensor using the configuration cable.
- Use the configuration cable (Item code: TTL-LRW-USB-01).
- Connect the USB-A plug into the USB-A socket of the PC.
Step 2:
On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none
Step 3:
Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.
Step 4:
Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.
Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.
Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.
Step 5:
Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.
Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type
Note: If the sensor has SKU of WSLRWEX-PPS and hardware version 1 & 2, the sensor must be powered by batteries for configuration
Step 6:
Read the current value of the parameter with Modbus Function 3
At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
Step 7:
Write the new setting to the parameter with Modbus Function 16
Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;
Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.
Repeat Step 6 to read the setting of the parameter for double-checking.
Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.
Only read/ write registers are allowed to write.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
4. Troubleshooting
3.3 Calibration/ Validation
How to force sensor to send data for calibration/ validation (if available)
Using the magnet key, the device can be triggered to send data to the gateway immediately.
Note:
Upon transmitting the data to the gateway using the magnetic key, the timer for the transmission time interval will be reset.
The minimum time interval between two manual triggers is 15 seconds. If the interval is less than 15 seconds, data transmission will not occur.
Calibration/ Validation sensor (if available)
No calibration is required for RS485 Modbus converter
4
PRODUCT SPECIFICATIONS
4.1 Specifications
| Input port | 1 x RS485 master port |
| Cable length | 2m, shielded cable with marking A & B wires |
| Protocol | Modbus RTU |
| Fault protected RS-485 bus pins | up to ±40V |
| HBM ESD protection on RS-485 bus pins | ±15kV |
| Extened common mode range | ±15V (larger than required for RS-485) |
| High transient over voltage tolerance | ±60V |
| Full fail-safe RS-485 receivers | open, short, terminated |
| COMMUNICATION | |
| SF Factors | SF7∼SF12 |
| Antenna | Internal Antenna 2.0 dbi |
| Battery | 02 x AA size 1.5VDC (battery not included) |
| RF Frequency and Power | 860∼930MHz, 14∼20dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AU915, US915 |
| Protocol | LoRaWAN, class A |
| Data sending modes | Interval time and when alarm occurred |
| Certification | CE, FCC |
| Working temperature | -40∼60℃ (with AA L91 Energizer®) |
| Dimensions | H180xW50xD40 |
| Net-weight | 250g |
| Housing | Polycarbonate & POM plastic, IP68 |
| Mounting | Wall mount |
5
WARRANTY & SUPPORT
5.1 Warranty
Warranty
Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.
Free Warranty Conditions
The manufacturer undertakes to guarantee within 12 months from shipment date.
Product failed due to defects in material or workmanship.
Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.
Note: One way shipping cost to the Return center shall be paid by Customers.
Paid Warranty
The warranty period has expired.
The product is not manufactured by Daviteq.
Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
Product damaged during shipment.
Product damaged due to faulty installation, usage, or power supply.
Product damage caused by the customer.
Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
Product damage is caused by unauthorized treatments and modifications.
Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.
5.2 Support
Support via Help center
If you need our support for Daviteq device's installation, configuration, test, and decode, please email us at: support@daviteq.com OR input support request at link: https://forms.office.com/r/XWHbYG7yy7
Our support engineer will contact you via email or the support ticket system.
If you have any questions about the product, you can search for information on our web (https://www.iot.daviteq.com/). If you can't find the right information, please register an account and send us a request at link Contact us | Daviteq Technologies . We will respond within 24 hours.